Ive been using Openhab 2.5 for a while 3 years without any problems, as an interface to connect Alexa (voice commands) to control my KNX system, which controls lighting and heating. I have a Viessman KNX gateway to the boiler, and I can use use the Openhab android app to control the Central Heating Set Point, and also the Hot Water temperature. I do have visulization KNX panel inside the house, which does the same thing really, but it is directly wired onto the KNX bus. I dont adjust them much, as they usually stay on 21 degs for Central Heating and 55 degs. Recently, say hte last couple of weeks, all of a sudden, sometimes its late a night, the Hot Water receives a command (looking at the logs) to raise the DHW temp to 75 degs and CH the set point to 25deg. I quickly then open the openhab app and adjust them back to 21 and 55 degs. I have it once, where light at night say 1.00am in the morning its turned all the lights on in the house, all of sudden. I thought first of all, someone may have hacked the system, either via Alexa account or Openhab account. I then thought it might be fault with the openhab app, as I thought it did it, as soon as I used the app remotely. I reinstalled the app, and cleared the cache, and it was fine for a week, but last night it did it again, out of nowhere at 1.00 am in the morning the DHW temp was raised to 75 deg and CH set point temp set to 23 degress. On the logs it shows as follows:
2023-01-31 01:01:33.334 [ome.event.ItemCommandEvent] - Item 'Hot_Water_Set_Point' received command 74.0
2023-01-31 01:01:33.407 [nt.ItemStatePredictedEvent] - Hot_Water_Set_Point predicted to become 74.0
2023-01-31 01:01:47.638 [ome.event.ItemCommandEvent] - Item 'Heating_Set_Point' received command 22.0
2023-01-31 01:01:47.668 [nt.ItemStatePredictedEvent] - Heating_Set_Point predicted to become 22.0
2023-01-31 01:01:47.696 [vent.ItemStateChangedEvent] - Heating_Set_Point changed from 23.0 to 22.0
2023-01-31 01:01:47.860 [ome.event.ItemCommandEvent] - Item 'Heating_Set_Point' received command 21.0
Any ideas, where this command has come from? What does [ome.event.ItemCommandEvent] mean? Has this come from Openhab via the app?
It also looks like it did it earlier in the night as well:
2023-01-30 23:19:26.714 [ome.event.ItemCommandEvent] - Item 'Heating_Set_Point' received command 21
2023-01-30 23:19:26.848 [nt.ItemStatePredictedEvent] - Heating_Set_Point predicted to become 21
2023-01-30 23:19:26.892 [vent.ItemStateChangedEvent] - Heating_Set_Point changed from 20.0 to 21
2023-01-30 23:19:26.899 [ome.event.ItemCommandEvent] - Item 'Heating_Set_Point' received command 22
2023-01-30 23:19:26.946 [nt.ItemStatePredictedEvent] - Heating_Set_Point predicted to become 22
2023-01-30 23:19:26.971 [vent.ItemStateChangedEvent] - Heating_Set_Point changed from 21 to 22
2023-01-30 23:19:27.062 [ome.event.ItemCommandEvent] - Item 'Heating_Set_Point' received command 22
2023-01-30 23:19:27.085 [nt.ItemStatePredictedEvent] - Heating_Set_Point predicted to become 22
2023-01-30 23:19:27.201 [ome.event.ItemCommandEvent] - Item 'Heating_Set_Point' received command 23
2023-01-30 23:19:27.232 [nt.ItemStatePredictedEvent] - Heating_Set_Point predicted to become 23
2023-01-30 23:19:27.247 [vent.ItemStateChangedEvent] - Heating_Set_Point changed from 22 to 23
2023-01-30 23:19:27.358 [ome.event.ItemCommandEvent] - Item 'Heating_Set_Point' received command 24
2023-01-30 23:19:27.383 [nt.ItemStatePredictedEvent] - Heating_Set_Point predicted to become 24
2023-01-30 23:19:27.397 [vent.ItemStateChangedEvent] - Heating_Set_Point changed from 23 to 24
2023-01-30 23:19:27.518 [ome.event.ItemCommandEvent] - Item 'Heating_Set_Point' received command 25
2023-01-30 23:19:27.542 [nt.ItemStatePredictedEvent] - Heating_Set_Point predicted to become 25
2023-01-30 23:19:27.562 [vent.ItemStateChangedEvent] - Heating_Set_Point changed from 24 to 25
2023-01-30 23:19:28.185 [ome.event.ItemCommandEvent] - Item 'Heating_Set_Point' received command 24
2023-01-30 23:19:28.212 [nt.ItemStatePredictedEvent] - Heating_Set_Point predicted to become 24
2023-01-30 23:19:28.230 [vent.ItemStateChangedEvent] - Heating_Set_Point changed from 25 to 24
2023-01-30 23:19:29.064 [ome.event.ItemCommandEvent] - Item 'Heating_Set_Point' received command 23
2023-01-30 23:19:29.128 [nt.ItemStatePredictedEvent] - Heating_Set_Point predicted to become 23
2023-01-30 23:19:29.147 [vent.ItemStateChangedEvent] - Heating_Set_Point changed from 24 to 23
2023-01-30 23:19:30.276 [ome.event.ItemCommandEvent] - Item 'Hot_Water_Set_Point' received command 56
2023-01-30 23:19:30.318 [nt.ItemStatePredictedEvent] - Hot_Water_Set_Point predicted to become 56
2023-01-30 23:19:30.348 [vent.ItemStateChangedEvent] - Hot_Water_Set_Point changed from 55.0 to 56
2023-01-30 23:19:30.442 [ome.event.ItemCommandEvent] - Item 'Hot_Water_Set_Point' received command 57
2023-01-30 23:19:30.464 [nt.ItemStatePredictedEvent] - Hot_Water_Set_Point predicted to become 57
2023-01-30 23:19:30.481 [vent.ItemStateChangedEvent] - Hot_Water_Set_Point changed from 56 to 57
2023-01-30 23:19:30.600 [ome.event.ItemCommandEvent] - Item 'Hot_Water_Set_Point' received command 58
2023-01-30 23:19:30.635 [nt.ItemStatePredictedEvent] - Hot_Water_Set_Point predicted to become 58
2023-01-30 23:19:30.669 [vent.ItemStateChangedEvent] - Hot_Water_Set_Point changed from 57 to 58
2023-01-30 23:19:30.772 [ome.event.ItemCommandEvent] - Item 'Hot_Water_Set_Point' received command 59
2023-01-30 23:19:30.791 [nt.ItemStatePredictedEvent] - Hot_Water_Set_Point predicted to become 59
2023-01-30 23:19:30.806 [vent.ItemStateChangedEvent] - Hot_Water_Set_Point changed from 58 to 59
2023-01-30 23:19:30.948 [ome.event.ItemCommandEvent] - Item 'Hot_Water_Set_Point' received command 60
2023-01-30 23:19:30.970 [nt.ItemStatePredictedEvent] - Hot_Water_Set_Point predicted to become 60
2023-01-30 23:19:30.983 [vent.ItemStateChangedEvent] - Hot_Water_Set_Point changed from 59 to 60
2023-01-30 23:19:31.104 [ome.event.ItemCommandEvent] - Item 'Hot_Water_Set_Point' received command 61
2023-01-30 23:19:31.138 [nt.ItemStatePredictedEvent] - Hot_Water_Set_Point predicted to become 61
2023-01-30 23:19:31.161 [vent.ItemStateChangedEvent] - Hot_Water_Set_Point changed from 60 to 61
2023-01-30 23:19:31.269 [ome.event.ItemCommandEvent] - Item 'Hot_Water_Set_Point' received command 62
2023-01-30 23:19:31.289 [nt.ItemStatePredictedEvent] - Hot_Water_Set_Point predicted to become 62
2023-01-30 23:19:31.303 [vent.ItemStateChangedEvent] - Hot_Water_Set_Point changed from 61 to 62
2023-01-30 23:19:31.412 [ome.event.ItemCommandEvent] - Item 'Hot_Water_Set_Point' received command 63
2023-01-30 23:19:31.429 [nt.ItemStatePredictedEvent] - Hot_Water_Set_Point predicted to become 63
2023-01-30 23:19:31.441 [vent.ItemStateChangedEvent] - Hot_Water_Set_Point changed from 62 to 63
2023-01-30 23:19:31.588 [ome.event.ItemCommandEvent] - Item 'Hot_Water_Set_Point' received command 64
2023-01-30 23:19:31.605 [nt.ItemStatePredictedEvent] - Hot_Water_Set_Point predicted to become 64
2023-01-30 23:19:31.620 [vent.ItemStateChangedEvent] - Hot_Water_Set_Point changed from 63 to 64
2023-01-30 23:19:31.750 [ome.event.ItemCommandEvent] - Item 'Hot_Water_Set_Point' received command 65
2023-01-30 23:19:31.768 [nt.ItemStatePredictedEvent] - Hot_Water_Set_Point predicted to become 65
2023-01-30 23:19:31.781 [vent.ItemStateChangedEvent] - Hot_Water_Set_Point changed from 64 to 65
2023-01-30 23:19:31.942 [ome.event.ItemCommandEvent] - Item 'Hot_Water_Set_Point' received command 66
2023-01-30 23:19:31.978 [nt.ItemStatePredictedEvent] - Hot_Water_Set_Point predicted to become 66
2023-01-30 23:19:32.001 [vent.ItemStateChangedEvent] - Hot_Water_Set_Point changed from 65 to 66
2023-01-30 23:19:32.092 [ome.event.ItemCommandEvent] - Item 'Hot_Water_Set_Point' received command 67
2023-01-30 23:19:32.110 [nt.ItemStatePredictedEvent] - Hot_Water_Set_Point predicted to become 67
2023-01-30 23:19:32.122 [vent.ItemStateChangedEvent] - Hot_Water_Set_Point changed from 66 to 67
2023-01-30 23:19:32.254 [ome.event.ItemCommandEvent] - Item 'Hot_Water_Set_Point' received command 68
2023-01-30 23:19:32.272 [nt.ItemStatePredictedEvent] - Hot_Water_Set_Point predicted to become 68
2023-01-30 23:19:32.287 [vent.ItemStateChangedEvent] - Hot_Water_Set_Point changed from 67 to 68
2023-01-30 23:19:32.411 [ome.event.ItemCommandEvent] - Item 'Hot_Water_Set_Point' received command 69
2023-01-30 23:19:32.430 [nt.ItemStatePredictedEvent] - Hot_Water_Set_Point predicted to become 69
2023-01-30 23:19:32.447 [vent.ItemStateChangedEvent] - Hot_Water_Set_Point changed from 68 to 69
2023-01-30 23:19:32.586 [ome.event.ItemCommandEvent] - Item 'Hot_Water_Set_Point' received command 70
2023-01-30 23:19:32.603 [nt.ItemStatePredictedEvent] - Hot_Water_Set_Point predicted to become 70
2023-01-30 23:19:32.617 [vent.ItemStateChangedEvent] - Hot_Water_Set_Point changed from 69 to 70
2023-01-30 23:19:32.734 [ome.event.ItemCommandEvent] - Item 'Hot_Water_Set_Point' received command 71
2023-01-30 23:19:32.750 [nt.ItemStatePredictedEvent] - Hot_Water_Set_Point predicted to become 71
2023-01-30 23:19:32.764 [vent.ItemStateChangedEvent] - Hot_Water_Set_Point changed from 70 to 71
2023-01-30 23:19:32.939 [ome.event.ItemCommandEvent] - Item 'Hot_Water_Set_Point' received command 72
2023-01-30 23:19:32.971 [nt.ItemStatePredictedEvent] - Hot_Water_Set_Point predicted to become 72
2023-01-30 23:19:32.995 [vent.ItemStateChangedEvent] - Hot_Water_Set_Point changed from 71 to 72
2023-01-30 23:19:33.084 [ome.event.ItemCommandEvent] - Item 'Hot_Water_Set_Point' received command 73
2023-01-30 23:19:33.100 [nt.ItemStatePredictedEvent] - Hot_Water_Set_Point predicted to become 73
2023-01-30 23:19:33.115 [vent.ItemStateChangedEvent] - Hot_Water_Set_Point changed from 72 to 73
2023-01-30 23:19:33.251 [ome.event.ItemCommandEvent] - Item 'Hot_Water_Set_Point' received command 74
2023-01-30 23:19:33.269 [nt.ItemStatePredictedEvent] - Hot_Water_Set_Point predicted to become 74
2023-01-30 23:19:33.284 [vent.ItemStateChangedEvent] - Hot_Water_Set_Point changed from 73 to 74
2023-01-30 23:19:33.434 [ome.event.ItemCommandEvent] - Item 'Hot_Water_Set_Point' received command 75
2023-01-30 23:19:33.457 [nt.ItemStatePredictedEvent] - Hot_Water_Set_Point predicted to become 75
2023-01-30 23:19:33.470 [vent.ItemStateChangedEvent] - Hot_Water_Set_Point changed from 74 to 75
2023-01-30 23:19:33.620 [ome.event.ItemCommandEvent] - Item 'Hot_Water_Set_Point' received command 75
2023-01-30 23:19:33.641 [nt.ItemStatePredictedEvent] - Hot_Water_Set_Point predicted to become 75
2023-01-30 23:19:33.800 [ome.event.ItemCommandEvent] - Item 'Hot_Water_Set_Point' received command 75
2023-01-30 23:19:33.845 [nt.ItemStatePredictedEvent] - Hot_Water_Set_Point predicted to become 75
2023-01-30 23:19:33.956 [ome.event.ItemCommandEvent] - Item 'Hot_Water_Set_Point' received command 75
2023-01-30 23:19:33.990 [nt.ItemStatePredictedEvent] - Hot_Water_Set_Point predicted to become 75
2023-01-30 23:19:34.144 [ome.event.ItemCommandEvent] - Item 'Hot_Water_Set_Point' received command 75
2023-01-30 23:19:34.161 [nt.ItemStatePredictedEvent] - Hot_Water_Set_Point predicted to become 75
2023-01-30 23:19:34.322 [ome.event.ItemCommandEvent] - Item 'Hot_Water_Set_Point' received command 75
2023-01-30 23:19:34.338 [nt.ItemStatePredictedEvent] - Hot_Water_Set_Point predicted to become 75
2023-01-30 23:19:34.445 [vent.ItemStateChangedEvent] - Middle_Bed_Current_Temp changed from 20.48 to 20.400000000000002
2023-01-30 23:19:34.505 [ome.event.ItemCommandEvent] - Item 'Hot_Water_Set_Point' received command 75
2023-01-30 23:19:34.530 [nt.ItemStatePredictedEvent] - Hot_Water_Set_Point predicted to become 75
2023-01-30 23:19:34.696 [ome.event.ItemCommandEvent] - Item 'Hot_Water_Set_Point' received command 75
2023-01-30 23:19:34.713 [nt.ItemStatePredictedEvent] - Hot_Water_Set_Point predicted to become 75
2023-01-30 23:19:34.862 [ome.event.ItemCommandEvent] - Item 'Hot_Water_Set_Point' received command 75
2023-01-30 23:19:34.893 [nt.ItemStatePredictedEvent] - Hot_Water_Set_Point predicted to become 75
2023-01-30 23:19:35.047 [ome.event.ItemCommandEvent] - Item 'Hot_Water_Set_Point' received command 75
2023-01-30 23:19:35.080 [nt.ItemStatePredictedEvent] - Hot_Water_Set_Point predicted to become 75
2023-01-30 23:19:35.210 [ome.event.ItemCommandEvent] - Item 'Hot_Water_Set_Point' received command 75
2023-01-30 23:19:35.246 [nt.ItemStatePredictedEvent] - Hot_Water_Set_Point predicted to become 75
2023-01-30 23:19:38.623 [ome.event.ItemCommandEvent] - Item 'Boiler_Operation_Mode' received command 3
2023-01-30 23:19:38.654 [nt.ItemStatePredictedEvent] - Boiler_Operation_Mode predicted to become 3
2023-01-30 23:19:38.675 [vent.ItemStateChangedEvent] - Boiler_Operation_Mode changed from 4.0 to 3
To add on what @binderth said, you can check the app log (go to app settings and scroll to bottom, then open the log from there). If it sends commands, it’ll log that there:
01-31 15:27:02.271 11534 21317 D WidgetAdapter: Command 'OFF' was sent successfully to https://demo.openhab.org/rest/items/DemoSwitch
01-31 15:27:02.769 11534 11581 D WidgetAdapter: Command 'ON' was sent successfully to https://demo.openhab.org/rest/items/DemoSwitch
Thanks, will check. Say if it was a voice command from Alexa, would that show up in the app log? I assume Alexa Openhab skill just controls the app directly, converting voice commands to commands via the app. I have no rules set for openhab, unless something has sneaked in there, and I need to check it, but the times it does it, seems to be arbitrary, and changes, sometimes its at 1.00 am in the morning, one time it was 2.00pm in the afternoon. I never really use the UI at all to control anything directly and have not got HABpanel set up either.
See, if there’s a pattern and work towards the culprit
Turn off devices and observe the outcome
Ad1.
I don’t know if there’s an user accesible log for your amazon account regarding Alexa stuff. The amazonechocontrol binding surely logs stuff, but only if it reached openhab or originates from it
You could run a KNX log (busmonitor on your ETS, if you have one) and see what knx address the telegram originates from
Ad2.
If it’s at the same time every day or if some other (KNX) item/sensor reaches a threshold… you could then work with that
Ad3.
Turn off your alexa (completely, meaning all possibly alexa skills and routines and stuff)
Turn off your KNX visu/panel and see what happens
My 2cents: it’s coming from some kind of KNX logic. Thermostat, panel logic,… something you changed recently?
I’ve always struggled with getting the bus monitor to work on my ETS 5.6, every time i’ve tried to use it, it says its not accessible via the KNX router but group address monitor works. Again you need to leave ETS running for it to log.
It never seems to be at the same time. It has done the same thing at 2.00pm in the afternoon and 1.00am in the morning. It has sometimes switched all the lights on as well. Really strange.
I will disable the Alexa Openhab skill on Alexa to see if it happens again
My 2cents: I think it might be the viessmann knx gateway to the boiler, which maybe failing and its getting confused and sending out commands to the boiler when it shouldnt be.
I’ve just logged into using the app, and its changed again, its set the hot water temp to 75 deg C and set point temp to 23, and changed the boiler mode to different setting. I think its the viessmann KNX gateway thats going wrong, must be!
I don’t know the Viessmann KNX gateway, is it some kind of hardware, which connects the Viessmann boiler with KNX? Does it have any logic built into it?
Would be a good way:
setup the group monitor in ETS
open openHAB App
see what happens
3.1 you’ve got the origin KNX addresses of all telegrams
3.2 pick the telegrams changing the values of the Viessmann boiler
3.3 trace it to a hardware
3.4 if it’s repeatedly doing the same thing, try to figure out, how it’s parametrized within the ETS (if it’s the Viessmann KNX gateway, that is)
Its a gateway between the viessmann boiler bus (121) to KNX, you can adjust the CH set point temperature, the DHW set point temperature, adjust heating curves for weather compensation mode, change mode off the boiler, say all off, DHW on/ CH off, CH Norm temp/night mode. Report boiler flow temperatures etc. Its been working fine for 8 years, and say 3 to 4 years with openhab an alexa. Alexa is not set up to change any of the stuff on the KNX viessmann gateway, its either done the Visu panel KNX on the KNX bus or the openhab app.
I also worked backed through the logs and it started happening on 19 January this year. I noticed the openhab app on android was recently updated 7 days ago.
I will need to check the KNX Visu Panel, to see if that is sending out weird KNX telegrams, when it feels like it. There is some logic in the Visu Panel for control of a DHW recirculation pump, and light switches and there are time programs to change the KNX room thermostats to different comfort modes, and night mode.
I left the group address monitor running last night on the KNX system and at 00.14, there was a group address which is my KNX IP/router (one of the address the KNX allocates to it) sending out groupwrite commands. Not only did it adjust the DHW temp, CH Set Point temp, it turned on the external lights to the front entrance door and roof terrace.
2892 1/2/2023 00:14:12.124 from bus Low 1.1.241 - 13/2/2007 DHW Temp Adj. 6 GroupValueWrite 9.001 temp… 15 78 | 56 °C
2893 1/2/2023 00:14:12.262 from bus Low 1.1.241 - 13/2/2007 DHW Temp Adj. 6 GroupValueWrite 9.001 temp… 15 91 | 57 °C
2894 1/2/2023 00:14:12.410 from bus Low 1.1.241 - 13/2/2007 DHW Temp Adj. 6 GroupValueWrite 9.001 temp… 15 AA | 58 °C
2895 1/2/2023 00:14:12.567 from bus Low 1.1.241 - 13/2/2007 DHW Temp Adj. 6 GroupValueWrite 9.001 temp… 15 C3 | 59 °C
2896 1/2/2023 00:14:12.739 from bus Low 1.1.241 - 13/2/2007 DHW Temp Adj. 6 GroupValueWrite 9.001 temp… 15 DC | 60 °C
2897 1/2/2023 00:14:12.947 from bus Low 1.1.241 - 13/2/2007 DHW Temp Adj. 6 GroupValueWrite 9.001 temp… 15 F5 | 61 °C
2898 1/2/2023 00:14:13.072 from bus Low 1.1.241 - 13/2/2007 DHW Temp Adj. 6 GroupValueWrite 9.001 temp… 16 0E | 62 °C
2899 1/2/2023 00:14:13.270 from bus Low 1.1.241 - 13/2/2007 DHW Temp Adj. 6 GroupValueWrite 9.001 temp… 16 27 | 63 °C
2900 1/2/2023 00:14:13.397 from bus Low 1.1.241 - 13/2/2007 DHW Temp Adj. 6 GroupValueWrite 9.001 temp… 16 40 | 64 °C
2901 1/2/2023 00:14:13.563 from bus Low 1.1.241 - 13/2/2007 DHW Temp Adj. 6 GroupValueWrite 9.001 temp… 16 59 | 65 °C
2902 1/2/2023 00:14:13.756 from bus Low 1.1.241 - 13/2/2007 DHW Temp Adj. 6 GroupValueWrite 9.001 temp… 16 72 | 66 °C
2903 1/2/2023 00:14:13.883 from bus Low 1.1.241 - 13/2/2007 DHW Temp Adj. 6 GroupValueWrite 9.001 temp… 16 8B | 67 °C
2904 1/2/2023 00:14:14.052 from bus Low 1.1.241 - 13/2/2007 DHW Temp Adj. 6 GroupValueWrite 9.001 temp… 16 A4 | 68 °C
So, from this it has got to be one of the following:
a) Openhab on PI is chucking out spurious commands
b) Alexa is chucking out spurious commands
c) Someone is getting access/hacking my KNX Ip/router and controlling it
As we confirmed yesterday its not the openhab app, as you need to be logged into it for it to send commands.