My main use is ‘write’ rather than ‘read’, avoiding the need to enable control outside my LAN. For example, I have a Zwave device defined in my *.items as:
Hmm. Looks like on mycroft-core v19.8.4, Current Temperature isn’t working.
I have tagged a few more temp sensors with ["CurrentTemperature"] as above, and SSH’d directly into a Mark_1, used mycroft-cli-client to inject speech commands:
refresh openhab items
>> All right. I found 21 items.
list openhab items
>> Found the following items:
Lights: Bedside Light <and others>
Switches: Good Night <and others>
Current Temperature: Inside, Radiator <and others>
Sadly, What's Radiator temperature? just gives a generic weather forecast - suggests some Padatious hacking may be needed to register the extra intents.
MDAR
(Stuart Hanlon, UK importer of Velbus hardware)
46
Yup… that’s what I’m getting too…
If you do find a way to resolve this, I’d be very interested.
Hi there. Following the issue, I tried to review the “what’s the status” intent, switching to the other way available in mycroft to define an intent (it uses a Machine Learning algorithm to decide the right skill). I also added new “questions formula” in order to have more way to ask the same thing and, f.i:
Hey Mycroft, what is the status of Switch? Hey Mycroft, tell me the temperature of Bedroom Hey Mycroft, I’d like to know the humidity of Bedroom
I made some test and it seems to be better. Could any of you make also some test? I’d appreciate that before to release the new version. If interested, I have a new branch in my github repository, can be installed manually typing:
Just got spammed that it’s selling now.
Do you have any information that you can share now ?
With SNIPS just dying thanks to Sonos a number of people are worried how to proceed to voice enable their homes.
MDAR
(Stuart Hanlon, UK importer of Velbus hardware)
50
Hi
Thanks for this.
I understand what you are trying to achieve, but I don’t understand what I’m supposed to do to add this functionality.
for example, which directory should I be cloning you repo into ?
(For to ask basic questions, I really am very new to Mycroft)
Hi @MDAR,
after other test I decided to release the fix. I submitted the skill to v19, so you’ll get the update when will be accepted, or follow the steps:
@MDAR Hi Stuart,
thanks for the speedy response,
Yes, I read it in detail and also the homekit tagging advice and the hue tagging pages - it may be a simple oversight on my side but after many many hours I’m no further forward on why non-light hue items are not discovered by the mycroft ‘refresh openhab items’ request.
MDAR
(Stuart Hanlon, UK importer of Velbus hardware)
56
I think you probably missed the part that shows the correct tags (I assume these are correct and that Mycroft hasn’t moved to Metadata yet)
Group gMyThermostat "My Thermostat"
Number ThermostatCurrentTemp "Thermostat Current Temperature" (gMyThermostat) ["CurrentTemperature"] {channel="Your Item"}
Number ThermostatTargetTemperature "Thermostat Target Temperature" (gMainThermostat) ["TargetTemperature"] {channel="Your Item"}
String ThermostatHeatingCoolingMode "Thermostat Heating/Cooling Mode" (gMyThermostat) ["homekit:HeatingCoolingMode"] {channel="Your Item"}
hi @MDAR
awesome - thanks - I was looking at the tag lists and trying to work out what what deprecated - whether to use metadata or not - mycroft now lists the items as recognised - unfortunately any variation of asking for temperatures now gives the external weather temperature
It looks like i am getting the same issue #85 as @FloatingBoater documented…
checking openhab items via SSH shows
Current Temperature: Middle floor, Ground floor, Top floor
and in response to
What's the temperature of Middle floor
>> It's currently 8 degrees celsius.
whats top floor temperature
>> It's currently 8 degrees celsius.
tell me the temperature of Top floor
>> It's currently 8 degrees celsius.
but the openhab log shows this error on updating the related thing file
2020-11-20 15:16:57.897 [ome.event.ItemUpdatedEvent] - Item 'F1_Hall_temp_sensor' has been updated.
==> /var/log/openhab2/openhab.log <==
2020-11-20 15:16:57.902 [ERROR] [ore.common.registry.AbstractRegistry] - Cannot inform the listener "org.openhab.io.hueemulation.internal.rest.Sensors@18848bb" about the "UPDATED" event: Item type not supported as sensor
java.lang.IllegalArgumentException: Item type not supported as sensor
at org.openhab.io.hueemulation.internal.dto.HueSensorEntry.<init>(HueSensorEntry.java:84) ~[?:?]
at org.openhab.io.hueemulation.internal.rest.Sensors.updated(Sensors.java:141) ~[?:?]
at org.openhab.io.hueemulation.internal.rest.Sensors.updated(Sensors.java:1) ~[?:?]
at org.eclipse.smarthome.core.common.registry.AbstractRegistry.notifyListeners(AbstractRegistry.java:366) ~[?:?]
at org.eclipse.smarthome.core.common.registry.AbstractRegistry.notifyListenersAboutUpdatedElement(AbstractRegistry.java:387) ~[?:?]
at org.eclipse.smarthome.core.internal.items.ItemRegistryImpl.notifyListenersAboutUpdatedElement(ItemRegistryImpl.java:379) ~[?:?]
at org.eclipse.smarthome.core.internal.items.ItemRegistryImpl.notifyListenersAboutUpdatedElement(ItemRegistryImpl.java:1) ~[?:?]
at org.eclipse.smarthome.core.common.registry.AbstractRegistry.updated(AbstractRegistry.java:291) ~[?:?]
at org.eclipse.smarthome.core.common.registry.AbstractRegistry.updated(AbstractRegistry.java:1) ~[?:?]
at org.eclipse.smarthome.core.common.registry.AbstractProvider.notifyListeners(AbstractProvider.java:62) ~[?:?]
at org.eclipse.smarthome.core.common.registry.AbstractProvider.notifyListenersAboutUpdatedElement(AbstractProvider.java:87) ~[?:?]
at org.eclipse.smarthome.model.item.internal.GenericItemProvider.modelChanged(GenericItemProvider.java:398) ~[?:?]
at org.eclipse.smarthome.model.core.internal.ModelRepositoryImpl.notifyListeners(ModelRepositoryImpl.java:311) ~[?:?]
at org.eclipse.smarthome.model.core.internal.ModelRepositoryImpl.addOrRefreshModel(ModelRepositoryImpl.java:149) ~[?:?]
at org.eclipse.smarthome.model.core.internal.folder.FolderObserver.checkFile(FolderObserver.java:247) ~[?:?]
at org.eclipse.smarthome.model.core.internal.folder.FolderObserver.processWatchEvent(FolderObserver.java:310) ~[?:?]
at org.eclipse.smarthome.core.service.WatchQueueReader.lambda$3(WatchQueueReader.java:323) ~[?:?]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_265]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_265]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [?:1.8.0_265]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [?:1.8.0_265]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_265]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_265]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_265]
I don’t know if the subject has been discussed in this topic, but as I run toward some need of controling Mycroft, I made myself a Mycroft binding for OpenHAB. Maybe some of you would be interested ?
Dear All, has anybody managed to get Openhab working with Mycroft Mark II?
Openhab skill is missing from the list of available skills, cannot even enable it…
Thank you!
MDAR
(Stuart Hanlon, UK importer of Velbus hardware)
60
Does your comment suggest that your Mark II devices have arrived?
Yep, but for now it’s just a paperweight without Openhab integration!
I’d be happy to lend my device to somebody who’s willing to invest time to figure it out.
1 Like
MDAR
(Stuart Hanlon, UK importer of Velbus hardware)
62
I’m waiting for mine to arrive.
When it gets here, maybe we can work on it together?
